Apparatuses, systems and methods for electronic data logging

ABSTRACT

Apparatuses, systems, and methods are provided for electronic data logging. More particularly, apparatuses, systems, and methods are provide for electronic data logging which may incorporate a vehicle electronic device that may store data when the vehicle electronic device is not in communication with an external device and that may transmit data when the vehicle electronic device is in communication with an external device.

TECHNICAL FIELD

The present disclosure generally relates to apparatuses, systems, andmethods for electronic data logging. More particularly, the presentdisclosure relates to apparatuses, systems, and methods for electronicdata logging which incorporate a vehicle electronic device that storesdata when the vehicle electronic device is not in communication with anexternal device and that transmits data when the vehicle electronicdevice is in communication with an external device.

BACKGROUND

Electronic data logging systems are employed in a number of differentapplications, including logging operating data in process plants,logging weather related data, logging vehicle operation data, etc. Knownelectronic data logging systems typically acquire electronic data fromone of more sensors. The electronic data logging systems may store theelectronic data for later analysis.

Various Federal, State and local agencies (e.g., Department ofTransportation, Transportation Safety Administration, etc.) havedeveloped, and/or are developing, laws and rules that require electronicon-board recorder (EOBR) devices to be incorporated into commercialmotor vehicles (CMVs). In accordance with certain laws and rules, anEOBR may, for example, record data for generating hours of service (HOS)reports, driver vehicle inspection reports (DVIRs), international fueltax agreement (IFTA) reports, etc.

Because the new laws and rules require CMV operators to provide certaindata, loss of data is a concern. Known systems do not incorporatemechanisms to prevent loss of data.

SUMMARY

A vehicle electronic device may include a processor and a memory. Thevehicle electronic device may also include a vehicle data acquisitionmodule, stored on the memory, that, when executed by the processor,causes the processor to receive vehicle data. The vehicle data mayinclude vehicle odometer information and vehicle global positioningsystem information. The vehicle electronic device may further include atime data acquisition module, stored on the memory, that, when executedby the processor, causes the processor to receive time data. The timedata may include information related to a time of day. The vehicleelectronic device may further include a time-stamped vehicle datageneration module, stored on the memory, that, when executed by theprocessor, causes the processor to generate time-stamped vehicle data.The time-stamped vehicle data may include the vehicle data correlatedwith the time data. The vehicle electronic device may yet furtherinclude a personal data acquisition module, stored on the memory, that,when executed by the processor, causes the processor to receive personaldata. The personal data may include information associated with at leastone vehicle operator. The vehicle electronic device may even furtherinclude a correlated vehicle data generation module, stored on thememory, that, when executed by the processor, causes the processor togenerate correlated vehicle data. The correlated vehicle data may berepresentative of an association between the time-stamped vehicle dataand the personal data. The vehicle electronic device may also include apersonal electronic device availability determination module, stored onthe memory, that, when executed by the processor, causes the processorto determine whether the vehicle electronic device is communicativelycoupled with a personal electronic device. When the processor determinesthat the vehicle electronic device is communicatively coupled with apersonal electronic device, the processor may transmit the correlatedvehicle data to the personal electronic device. When the processordetermines that the vehicle electronic device is not communicativelycoupled with a personal electronic device, the processor may store thecorrelated vehicle data on the memory of the vehicle electronic device.

In another embodiment, a non-transitory, computer-readable, medium mayinclude a vehicle data acquisition module that, when executed by aprocessor, causes the processor to receive vehicle data at a vehicleelectronic device. The vehicle data may include vehicle odometerinformation and vehicle global positioning system information. Thenon-transitory, computer-readable, medium may also include a time dataacquisition module that, when executed by a processor, causes theprocessor to receive time data. The time data may include informationrelated to a time of day. The non-transitory, computer-readable, mediummay further include a time-stamped vehicle data generation module that,when executed by a processor, causes the processor to generatetime-stamped vehicle data. The time-stamped vehicle data may include thevehicle data correlated with the time data. The non-transitory,computer-readable, medium may yet further include a personal dataacquisition module that, when executed by a processor, causes theprocessor to receive personal data. The personal data may includeinformation associated with at least one vehicle operator. Thenon-transitory, computer-readable, medium may even further include apersonal electronic device availability determination module that, whenexecuted by the processor, causes the processor to determine whether thevehicle electronic device is communicatively coupled with a personalelectronic device. When the processor determines that the vehicleelectronic device is communicatively coupled with a personal electronicdevice, the processor may transmit the correlated vehicle data to thepersonal electronic device. When the processor determines that thevehicle electronic device is not communicatively coupled with a personalelectronic device, the processor may store the correlated vehicle dataon a memory of the vehicle electronic device.

In a further embodiment, an electronic data logging system may include apersonal electronic device having a first processor and a first memory.The personal electronic device may also include a personal dataacquisition module, stored on the first memory, that, when executed bythe first processor, causes the first processor to receive personaldata. The personal data may include information associated with at leastone vehicle operator. The personal electronic device may further includea personal data transmission module, stored on the first memory, that,when executed by the first processor, causes the first processor totransmit the personal data to a vehicle electronic device. The vehicleelectronic device may include a second processor and a second memory.The vehicle electronic device may also include a personal data receivingmodule, stored on the second memory, that, when executed by the secondprocessor, causes the second processor to receive the personal data fromthe first processor. The vehicle electronic device may further include avehicle data acquisition module, stored on the second memory, that, whenexecuted by the second processor, causes the second processor to receivevehicle data in response to receiving the personal data. The vehicledata may include at least one of: vehicle position data, vehicle enginerevolution per minute data, vehicle speed data, vehicle odometer data,or vehicle engine operating hour data. The vehicle electronic device mayyet further include a time data acquisition module, stored on the secondmemory, that, when executed by the second processor, causes the secondprocessor to receive time data. The time data may include informationrelated to a time of day. The vehicle electronic device may yet furtherinclude a time-stamped vehicle data generation module, stored on thesecond memory, that, when executed by the second processor, causes thesecond processor to generate time-stamped vehicle data. The time-stampedvehicle data includes the vehicle data correlated with the time data.The vehicle electronic device may even further include a personalelectronic device availability determination module, stored on thesecond memory, that, when executed by the second processor, causes thesecond processor to determine whether the vehicle electronic device iscommunicatively coupled with the personal electronic device. When thesecond processor determines that the vehicle electronic device iscommunicatively coupled with the personal electronic device, the secondprocessor may transmit the time-stamped vehicle data to the personalelectronic device. When the second processor determines that the vehicleelectronic device is not communicatively coupled with the personalelectronic device, the second processor may store the time-stampedvehicle data on the second memory.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an example electronic data logging system incorporatedinto a vehicle;

FIG. 2 depicts an example hours of service (HOS) report display;

FIG. 3 depicts an example vehicle gauges display;

FIG. 4 depicts an example electronic data logging system including aplurality of vehicle companies, a plurality of vehicles, a plurality ofvehicle electronic devices, a plurality of personal electronic devices,and a plurality of individual vehicle operators;

FIG. 5 depicts an example electronic data logging system including avehicle electronic device, a personal electronic device, and a remoteelectronic device (e.g., a remote server);

FIG. 6 depicts an example electronic data logging system including avehicle electronic device having external communications peripherals, apersonal electronic device, and a remote electronic device;

FIG. 7 depicts an example electronic data logging system including twovehicles, each vehicle having a respective vehicle electronic device incommunication with a respective personal electronic device, and a remoteelectronic device;

FIG. 8 depicts an example electronic data logging system including threevehicles, each vehicle having a respective vehicle electronic device incommunication with either a respective personal electronic device and/ora remote electronic device;

FIG. 9 depicts an example electronic data logging system including avehicle having a vehicle electronic device in communication with apersonal electronic device and a remote electronic device;

FIG. 10 depicts an example electronic data logging system including twovehicles, each vehicle having a respective vehicle electronic device incommunication with a respective personal electronic device and/or aremote electronic device;

FIG. 11 depicts a block diagram of an example electronic data loggingsystem;

FIG. 12 depicts a block diagram of an example personal electronicdevice;

FIG. 13 depicts a flow diagram of an example method of operating apersonal electronic device;

FIG. 14 depicts a block diagram of an example vehicle electronic device;

FIG. 15 depicts an flow diagram of an example method of storing and/ortransmitting electronic data;

FIG. 16 depicts a flow diagram of an example method of operating avehicle electronic device;

FIG. 17 depicts a block diagram of an example remote electronic device;and

FIG. 18 depicts a flow diagram of an example method of operating aremote electronic device.

DETAILED DESCRIPTION

Apparatuses, systems, and methods are provided for electronic datalogging. As described in detail herein, associated electronic data maybe acquired from a plurality of sensors (e.g., vehicle sensors), sources(e.g., a vehicle electronic control module), and user inputs. Theelectronic data may be correlated with associated time-of-day dataand/or associated vehicle operator data. The electronic data mayinclude, for example, any one of, all of, or any sub-combination ofengine control unit history data, air supply pressure data, fuelconsumption data, trip information data, vehicle speed data, vehiclecruise control status data, engine cooling fan drive status data, wheelspeed data, vehicle service indication data, transmission control unithistory data, body control unit history data, driver door statusindicator data, passenger door indicator data, engine oil level data,engine oil pressure data, engine idle operation data, turbochargerstatus data, air start pressure data, steering wheel angle data, vehicleaccelerometer data, vehicle pitch data, vehicle yaw data, vehicledistance data, idle shutdown data, engine hours data, engine revolutionsdata, time of day data, date of year data, vehicle hours data, vehicledirection data, vehicle speed data, fuel consumption data, vehicleweight data, cruise control speed set data, engine temperature data,power takeoff information data, fuel economy data, vehicle position(longitude/latitude/elevation) data, tire condition data, ambientconditions data, inlet air condition data, exhaust condition data,vehicle electrical power condition data, transmission fluid level data,transmission fluid pressure data, brake information data, engine coolantlevel data, engine coolant pressure data, vehicle odometer reading data,vehicle identification number data, crankcase pressure data, barometricpressure data, vehicle interior temperature data, air inlet temperaturedata, road surface temperature data, particulate trap inlet pressuredata, boost pressure data, intake manifold temperature data, air inletpressure data, air filter differential pressure data, exhaust gastemperature data, coolant filter differential pressure data,instantaneous fuel economy data, average fuel economy data, fueltemperature data, turbo oil temperature data, total fuel used data, tripfuel data, injector metering rail pressure data, injection controlpressure data, percent fan speed data, engine-percent torque demanddata, actual engine-percent torque data, accelerator pedal positiondata, percent load at current speed data, brake pedal position data,clutch pedal position data, water in fuel sensor data, etc.

As further described in detail herein, electronic data and/or correlatedelectronic data may be stored in, and/or transmitted from, a vehicleelectronic device (e.g., an electronic on-board recorder (EOBR)) to apersonal electronic device (e.g., a smartphone, a lap top computer, atablet computer, a special purpose electronic device, etc.) and/or aremote electronic device (e.g., a remote server). As yet furtherdescribed in detail herein, various reports (e.g., an hours of service(HOS) report, a driver vehicle inspection report (DVIR), aninternational fuel tax agreement (IFTA) report, etc.) and/or displays(e.g., an hours of service (HOS) display, a driver vehicle inspectionreport (DVIR) display, an international fuel tax agreement (IFTA)display, a vehicle gauges display, etc.) may be generated based onassociated electronic data and/or correlated electronic data.

Turning to FIG. 1, an electronic data logging system 100 may include avehicle 105 (e.g., a commercial motor vehicle) having an electroniccontrol module (ECM) 115. The electronic data logging system 100 mayfurther include a vehicle electronic device (e.g., an electronicon-board recorder (EOBR)) communicatively connected to the electroniccontrol module (ECM) 115 (e.g., an engine control module, a bodycontroller, etc.) via, for example, a vehicle bus (e.g., an OBDIIprotocol bus, a J1939 protocol bus, a J1708 protocol bus, etc.). Theelectronic data logging system 100 may also include a personalelectronic device 120 having an electronic data logging application 121.

As described in detail herein, a user of the personal electronic device120 may enter personal information (e.g., company data, vehicle operatordata, vehicle identification number (VIN) data, etc.). As analternative, vehicle identification number (VIN) data may beautomatically acquired from an electronic control module 115 when, forexample, the VIN data is available via the ECM 115. As further describedin detail herein, personal data representative of the personalinformation may be transmitted from the personal electronic device 120to the vehicle electronic device 110, thereby, the vehicle electronicdevice 110 may acquire vehicle data (e.g., vehicle location data,vehicle engine revolution per minute (RPM) data, vehicle speed data,vehicle odometer data, vehicle engine hour data, etc.) and time-of-daydata, and may correlate the vehicle data with the personal data and thetime-of-day data. As also described in detail herein, the vehicleelectronic device 110 may store correlated vehicle data and/or maytransmit the correlated vehicle data to the personal electronic device120 and/or a remote electronic device (not shown in FIG. 1).

With reference to FIG. 2, an electronic data logging system 200 mayinclude a personal electronic device 205. The personal electronic device205 may be similar to, for example, the personal electronic device 120of FIG. 1. The personal electronic device 205 may include an hours ofservice (HOS) report display 210 that may indicate a number of hours avehicle operator was off duty 211, a number of hours the vehicleoperator was in a sleeper birth 212, a number of hours the vehicleoperator was driving 213, and a number of hours the operator was on dutybut not driving 214. As described in detail herein, the HOS reportdisplay may be generated based on, for example, correlated vehicle datareceived from a vehicle electronic device (e.g., vehicle electronicdevice 110 of FIG. 1). The personal electronic device 210 may furtherinclude audible volume controls 215, operator interface controlinputs/indicators 216, a camera 220, a speaker 225, and a microphone230. The display of the personal electronic device 210 may be, forexample, any form of a known touch screen display or a non-touch screendisplay.

Turning to FIG. 3, an electronic data logging system 300 may include apersonal electronic device 305. The personal electronic device 305 maybe similar to, for example, the personal electronic device 120 of FIG. 1or the personal electronic device 205 of FIG. 2. The personal electronicdevice 305 may include a vehicle gauges display 310 having a pluralityof vehicle gauges 311. As described in detail herein, the vehicle gaugesdisplay 310 may be generated based on, for example, vehicle datareceived from a vehicle electronic device (e.g., vehicle electronicdevice 110 of FIG. 1). The personal electronic device 310 may furtherinclude audible volume controls 315, operator interface inputcontrols/indicators 316, a camera 320, a speaker 325, and a microphone330. The display of the personal electronic device 310 may be, forexample, any form of a known touch screen display or a non-touch screendisplay.

With reference to FIG. 4, an electronic data logging system 400 mayinclude a plurality of companies 405, 430. Any one of, or all of thecompanies 405, 430 may include a plurality of vehicles 410. Any one of,or all of the vehicles 410 may be similar to, for example, the vehicle105 of FIG. 1.

Any one of, or all of the vehicles 410 may include a vehicle electronicdevice 415 (e.g., an electronic logging device (ELD), an electronicon-board recorder (EOBR), etc.). Any one of, or all of the plurality ofvehicle electronic devices 415 may be similar to, for example, thevehicle electronic device 110 of FIG. 1. As described in detail herein,a first vehicle electronic device of the plurality of vehicle electronicdevices 415 may be correlated with a first individual of the pluralityof individuals 425, installed in a first vehicle of the plurality ofvehicles 410, and may acquire vehicle data from the first vehicle. Asfurther described in detail herein, subsequent to the first vehicleelectronic device being correlated with the first individual andacquiring vehicle data from the first vehicle, the first vehicleelectronic device may be removed from the first vehicle and installed ina second vehicle of the plurality of vehicles 410. Subsequent to beinginstalled in the second vehicle, the first vehicle electronic device mayacquire vehicle data from the second vehicle and correlate the vehicledata from the second vehicle with the first individual. Alternatively,the first vehicle electronic device may be recorrelated with a secondindividual and any subsequent vehicle data, that is acquired by thefirst vehicle electronic device, may be correlated with the secondindividual rather than the first individual.

As further illustrated in FIG. 4, any one of, or all of the companies405, 430 may include a plurality of personal electronic devices 420. Asdescribed in detail herein, any one of the plurality of personalelectronic devices 420 may be associated with any one of the individuals425. Alternatively, a plurality of personal electronic devices 420 maybe associated with any one of the individuals 425. The personalelectronic devices 420 may be similar to, for example, any one of thepersonal electronic devices 120, 205, 305 of FIGS. 1, 2 and 3,respectively.

Turning to FIG. 5, an electronic data logging system 500 may include avehicle electronic device 505 (e.g., a microcontroller (MCU) having anelectronic data logging application (or module) 514. The vehicleelectronic device 505 may be similar to, for example, any one of thepersonal electronic devices 120, 205, 305, 420 of FIGS. 1-4,respectively. The vehicle electronic device 505 may include a vehiclebus connector 510 having, for example, a CAN 2.0b XCVR interface 511and/or a J1708 (RS485) XCVR interface 512. The vehicle electronic device505 may also include an audible output to an audible device (e.g., aspeaker) 509, a visual output to a visual device 508 (e.g., an LED), aglobal positioning system (GPS) input from a GPS device 507, anaccelerometer input from an accelerometer sensor 506, and a storagememory 513.

As described in detail herein, the vehicle electronic device 505 mayacquire, for example, vehicle data, personal data and time-of-day data,and may correlate the vehicle data with the personal data and thetime-of-day data. The vehicle electronic device 505 may transmit thecorrelated vehicle data 521 to a personal electronic device 515 via awireless communication interface 520 (e.g., a BLUETOOTH® interface,WI-FI® interface, etc.). Alternatively, or additionally, the vehicleelectronic device 505 may store the correlated vehicle data in thestorage memory 513 when, for example, the personal electronic device 515is not communicatively coupled to the vehicle electronic device 505. Inlieu of, or in addition to, correlated vehicle data, the vehicleelectronic device 505 may transmit and/or store vehicle data that iscorrelated with only the vehicle information and/or time-of-day (i.e.,the vehicle data is not correlated with personal data).

As further described in detail herein, the personal electronic device515 may store the correlated vehicle data within a memory of thepersonal electronic device 515 and/or may transmit the correlatedvehicle data 521 via, for example, a cellular network connection 530 toa remote electronic device 525 (e.g., a remote server, a remotecomputing device, etc.). The remote electronic device 525 may store thecorrelated vehicle data in a memory 526. As described in detail herein,the personal electronic device 515 and the remote electronic device 525may periodically reconcile correlated vehicle data stored in thepersonal electronic device 515 with correlated vehicle data stored inthe memory 526 to, for example, insure that both versions include allavailable correlated vehicle data.

With reference to FIG. 6, an electronic data logging system 600 mayinclude a vehicle electronic device 605 having an electronic datalogging application (or electronic data logging module) 606 and arouting function (or routing module) 607. The vehicle electronic device605 may be similar to, for example, any one of the personal electronicdevices 120, 205, 305, 420, 505 of FIGS. 1-5, respectively. The vehicleelectronic device 605 may include a vehicle bus connector 615 having,for example, a CAN 2.0b XCVR interface 617 and/or a J1708 (RS485) XCVRinterface 616. The vehicle electronic device 605 may also include anaudible output (e.g., a speaker) 613, a visual output 612, a globalpositioning system (GPS) input 611, an accelerometer input 610, astorage memory 620, a near field communication module 625, and acellular communication module 635. The near field communication module625 (e.g., a short range radio module) may include a first wirelesscommunication interface 626 (e.g., a Bluetooth® interface) and a secondwireless communication interface 628 (e.g., a WI-FI® interface).

As described in detail herein, the vehicle electronic device 605 mayacquire, for example, vehicle data, personal data and time-of-day data,and may generate correlated vehicle data 627 based on the vehicle datawith the personal data and the time-of-day data. The vehicle electronicdevice 605 may transmit the correlated vehicle data 627 to a personalelectronic device 630 via a the first wireless communication interface626. Alternatively, or additionally, the vehicle electronic device 605may store the correlated vehicle data in the storage memory 620 when,for example, the personal electronic device 630 is not communicativelycoupled to the vehicle electronic device 605. In lieu of, or in additionto, correlated vehicle data 627, the vehicle electronic device 605 maytransmit and/or store vehicle data that is correlated with only thevehicle information and/or time-of-day (i.e., the vehicle data is notcorrelated with personal data).

As further described in detail herein, the personal electronic device630 may store the correlated vehicle data within a memory 631 of thepersonal electronic device 630 and/or may transmit the reconciledvehicle data via, for example, the second wireless communicationinterface 628, the routing function 607, the cellular communicationmodule 635, and the cellular communication network 637 to a remoteelectronic device 640 (e.g., a remote server, a remote computing device,etc.). The remote electronic device 640 may store the correlated vehicledata in, for example, a database table within memory 641. As describedin detail herein, the personal electronic device 630 and the remoteelectronic device 640 may periodically reconcile correlated vehicle datastored in the memory 631 with correlated vehicle data stored in thememory 641 to, for example, insure that both versions include allavailable correlated vehicle data.

As further illustrated in FIG. 6, the vehicle electronic device 605 maytransmit vehicle data and/or correlated vehicle data 636, via thecellular communication module 635 and a cloud based network, to theremote electronic device 640. As described in detail herein, the remoteelectronic device 640 may generate hours of service (HOS) data, an HOSreport, a driver vehicle inspection report (DVIR), international fueltax agreement (IFTA) data, or any combination thereof, based on thecorrelated vehicle data and/or vehicle data. As further described indetail herein, the remote electronic device 640 may transmit thecorrelated vehicle data and/or vehicle data to, for example, a vehiclemanufacture.

Turning to FIG. 7, an electronic data logging system 700 may include afirst vehicle 705 having a first vehicle electronic device 710configured to transmit first correlated vehicle data 717 to a firstpersonal electronic device 715 via a first communication link 711 (e.g.,a BLUETOOTH® link, a WI-FI® link, a USB link, etc.). The first personalelectronic device 715 may generate first hours of service (HOS) data, afirst HOS report, a first driver vehicle inspection report (DVIR), firstinternational fuel tax agreement (IFTA) data, a first gauges display716, or any combination thereof, based on the first correlated vehicledata and/or first vehicle data. The first personal electronic device 715may transmit the first vehicle data, the first correlated vehicle data,the first hours of service (HOS) data, the international fuel taxagreement (IFTA) data, or any combination thereof, to a remoteelectronic device 720 via a cloud based communication network 725 (e.g.,an Internet network). The remote electronic device 720 may store thefirst vehicle data, the first correlated vehicle data, the first hoursof service (HOS) data, the international fuel tax agreement (IFTA) data,or any combination thereof, on a memory 721. The first personalelectronic device 715 and the remote electronic device 720 mayperiodically transmit first correlated vehicle data 718 and secondcorrelated vehicle data 726 to, for example, reconcile the firstcorrelated vehicle data 718 and the second correlated vehicle data 726.

The electronic data logging system 700 may also include a second vehicle730 having a second vehicle electronic device 735 configured to transmitthird correlated vehicle data 742 to a second personal electronic device740 via a third communication link 736 (e.g., a BLUETOOTH® link, aWI-FI® link, a USB link, etc.). The second personal electronic device740 may generate second hours of service (HOS) data, a second HOSreport, a second driver vehicle inspection report (DVIR), secondinternational fuel tax agreement (IFTA) data, a second gauges display741, or any combination thereof, based on the third correlated vehicledata and/or second vehicle data. The second personal electronic device740 may transmit the second vehicle data, the second correlated vehicledata, the second hours of service (HOS) data, the second internationalfuel tax agreement (IFTA) data, or any combination thereof, to theremote electronic device 720 via a wireless modem 745 and the cloudbased communication network 725 (e.g., an Internet network). The remoteelectronic device 720 may store the second vehicle data, the thirdcorrelated vehicle data, the second hours of service (HOS) data, thesecond international fuel tax agreement (IFTA) data, or any combinationthereof, on the memory 721. The second personal electronic device 740and the remote electronic device 720 may periodically transmit thirdcorrelated vehicle data 743 and fourth correlated vehicle data 746 to,for example, reconcile the third correlated vehicle data 743 and thefourth correlated vehicle data 746.

With reference to FIG. 8, an electronic data logging system 800 mayinclude a first vehicle 805 having a first vehicle electronic device 810configured to transmit first correlated vehicle data 812 to a firstpersonal electronic device 815 via a first communication link 811 (e.g.,a BLUETOOTH® link, a WI-FI® link, a cellular link, etc.). The firstpersonal electronic device 815 may generate first hours of service (HOS)data, a first HOS report, a first driver vehicle inspection report(DVIR), first international fuel tax agreement (IFTA) data, a firstgauges display 816, or any combination thereof, based on the firstcorrelated vehicle data and/or first vehicle data. The first personalelectronic device 815 may transmit the first vehicle data, the firstcorrelated vehicle data, the first hours of service (HOS) data, theinternational fuel tax agreement (IFTA) data, or any combinationthereof, to a remote electronic device 825 via a cloud basedcommunication network 820 (e.g., an Internet network). The remoteelectronic device 825 may store the first vehicle data, the firstcorrelated vehicle data, the first hours of service (HOS) data, theinternational fuel tax agreement (IFTA) data, or any combinationthereof, on a memory 826. The first personal electronic device 815 andthe remote electronic device 825 may periodically transmit firstcorrelated vehicle data 817 and second correlated vehicle data 822 to,for example, reconcile the first correlated vehicle data 817 and thesecond correlated vehicle data 822. As further illustrated in FIG. 8,the first vehicle electronic device 810 may transmit the firstcorrelated vehicle data and/or first vehicle data 813 directly to thecloud network 820 (e.g., an Internet network, a wide area network (WAN),etc.) via a communication link 821 (e.g., a cellular network, asatellite network, etc.).

The electronic data logging system 800 may also include a second vehicle830 having a second vehicle electronic device 835 configured to transmitthird correlated vehicle data 837 to a second personal electronic device840 via a third communication link (e.g., a cellular network) 836. Thesecond personal electronic device 840 may generate second hours ofservice (HOS) data, a second HOS report, a second driver vehicleinspection report (DVIR), second international fuel tax agreement (IFTA)data, a second gauges display 841, or any combination thereof, based onthe third correlated vehicle data and/or second vehicle data. The secondpersonal electronic device 840 may transmit the second vehicle data, thesecond correlated vehicle data, the second hours of service (HOS) data,the second international fuel tax agreement (IFTA) data, or anycombination thereof, to the remote electronic device 825 via the cloudbased communication network 820 (e.g., an Internet network). The remoteelectronic device 825 may store the second vehicle data, the thirdcorrelated vehicle data, the second hours of service (HOS) data, thesecond international fuel tax agreement (IFTA) data, or any combinationthereof, on the memory 826. The second personal electronic device 840and the remote electronic device 825 may periodically transmit thirdcorrelated vehicle data 843 and fourth correlated vehicle data 842 to,for example, reconcile the third correlated vehicle data 843 and thefourth correlated vehicle data 842.

The electronic data logging system 800 may further include a thirdvehicle 845 having a third vehicle electronic device 850 communicativelycouple to the cloud based communication network 820 via a fifthcommunication link 852 to transmit fifth correlated vehicle data 851.The third personal electronic device 850 and the remote electronicdevice 825 may periodically transmit the fifth correlated vehicle data851 and sixth correlated vehicle data to, for example, reconcile thefifth correlated vehicle data 851 and the sixth correlated vehicle data.

Turning to FIG. 9, an electronic data logging system 900 may include afirst vehicle 905 having a first vehicle electronic device 910configured to transmit correlated vehicle data 914 to a personalelectronic device 915 via a first communication link 913 (e.g., aBLUETOOTH® link, a WI-FI® link, a USB link, etc.). The personalelectronic device 915 may generate second hours of service (HOS) data, asecond HOS report, a second driver vehicle inspection report (DVIR),second international fuel tax agreement (IFTA) data, a second gaugesdisplay 916, or any combination thereof, based on the third correlatedvehicle data and/or second vehicle data. The personal electronic device915 may transmit the vehicle data, the correlated vehicle data, thesecond hours of service (HOS) data, the second international fuel taxagreement (IFTA) data, or any combination thereof, to the remoteelectronic device 930 via a wireless communication link 917, a wirelessmodem 920 and the cloud based communication network 925 (e.g., anInternet network). The remote electronic device 930 may store the secondvehicle data, the third correlated vehicle data, the second hours ofservice (HOS) data, the second international fuel tax agreement (IFTA)data, or any combination thereof, on the memory 931. The personalelectronic device 915 and the remote electronic device 930 mayperiodically transmit the correlated vehicle data 914 and secondcorrelated vehicle data 926 to, for example, reconcile the correlatedvehicle data 914 and the second correlated vehicle data 926. As furtherillustrated in FIG. 9, the vehicle electronic device 910 may transmitthe correlated vehicle data and/or the vehicle data 912 directly to thecloud network 925 (e.g., an Internet network, a wide area network (WAN),etc.) via a communication link 911 (e.g., a cellular network, asatellite network, etc.).

With reference to FIG. 10, an electronic data logging system 1000 mayinclude a first vehicle 1005 having a first vehicle electronic device1010 configured to transmit first correlated vehicle data 1012 to afirst plurality of personal electronic device 1015 via a firstcommunication link 1011 (e.g., a BLUETOOTH® link, a WI-FI® link, a USBlink, etc.) or to a remote electronic device 1025 via a first vehicleelectronic device 1010, a communication link 1014, and a cloud basedcommunication network 1020 (e.g., an Internet network). Any one of, orall of, the first plurality of personal electronic devices 1015 maygenerate first hours of service (HOS) data, a first HOS report, a firstdriver vehicle inspection report (DVIR), first international fuel taxagreement (IFTA) data, a first gauges display 1016, or any combinationthereof, based on the first correlated vehicle data and/or first vehicledata. The first plurality of personal electronic devices 1015 maytransmit the first vehicle data, the first correlated vehicle data, thefirst hours of service (HOS) data, the international fuel tax agreement(IFTA) data, or any combination thereof, to a remote electronic device1025 via the first vehicle electronic device 1010 and a cloud basedcommunication network 1020 (e.g., an Internet network). The remoteelectronic device 1025 may store the first vehicle data, the firstcorrelated vehicle data, the first hours of service (HOS) data, theinternational fuel tax agreement (IFTA) data, or any combinationthereof, on a memory 1026. The first plurality of personal electronicdevice 1015 and the remote electronic device 1025 may periodicallytransmit first correlated vehicle data 1013 and second correlatedvehicle data 1021 to, for example, reconcile the first correlatedvehicle data 1013 and the second correlated vehicle data 1021.

The electronic data logging system 1000 may also include a secondvehicle 1030 having a second vehicle electronic device 1035 configuredto transmit third correlated vehicle data to a second personalelectronic device 1040 via a third communication link 1036 (e.g., aBLUETOOTH® link, a WI-FI® link, a USB link, etc.). The second personalelectronic device 1040 may generate second hours of service (HOS) data,a second HOS report, a second driver vehicle inspection report (DVIR),second international fuel tax agreement (IFTA) data, a second gaugesdisplay 741, or any combination thereof, based on the third correlatedvehicle data and/or second vehicle data. The second personal electronicdevice 1040 may transmit the second vehicle data, the second correlatedvehicle data, the second hours of service (HOS) data, the secondinternational fuel tax agreement (IFTA) data, or any combinationthereof, to the remote electronic device 1025 via the cloud basedcommunication network 1020. The remote electronic device 1025 may storethe second vehicle data, the third correlated vehicle data, the secondhours of service (HOS) data, the second international fuel tax agreement(IFTA) data, or any combination thereof, on the memory 1026. The secondpersonal electronic device 1040 and the remote electronic device 1025may periodically transmit third correlated vehicle data 1042 and fourthcorrelated vehicle data 1021 to, for example, reconcile the thirdcorrelated vehicle data 1042 and the fourth correlated vehicle data1021.

Turning to FIG. 11, an electronic data logging system 1100 (e.g., anhours service (HOS) calculator engine) may be incorporated into, forexample, a personal electronic device (e.g., personal electronic device120 of FIG. 1) and may include an input pre-processor 1105 configured toreceive a server input 1106, a user input 1107, and a vehicle electronicdevice input 1108, and further configured to process requests, queuerequests, manage priority, and maintain data for the requests. Theelectronic data logging system 1100 may also include a logger 1110,timers 1115 (e.g., work timers, break timers, etc.) an hours of service(HOS) processor 1120 (e.g., a processing state machine), an hours ofservice (HOS) manager 1125 for supervisory functions and error handling,a database connector 1130, a database 1135, and an hours of service(HOS) calculator 1140 (e.g., a rule engine) for receiving ruleconfiguration 1141.

With referenced to FIG. 12, an electronic data logging system 1200 mayinclude a personal electronic device 1205 having a user interfacegeneration module 1210; a vehicle operator data receiving module 1213; avehicle operator data transmission module 1215; a vehicle identificationnumber (VIN) data receiving module 1217; a VIN data transmission module1220; an electronic data logging device—vehicle data configurationmodule 1223; an electronic data logging device—vehicle dataconfiguration transmission module 1225; a vehicle data receiving module1227; a time of day data receiving module 1230; a vehicle data, VINdata, vehicle operator data, and time of day data correlation module1232; a correlated data receiving module 1235; a correlated datareconciliation module 1238; an hours of service (HOS) data generationmodule 1240; a gauges data generation module 1242; a driver vehicleinspection report (DVIR) data generation module 1245; an internationalfuel tax agreement (IFTA) data generation module 1247; a report datageneration module 1250; a report data transmission module 1252; and areport data receiving module 1255, stored on, for example, anon-transitory computer-readable medium 1207 in a form ofcomputer-readable instructions.

While the user interface generation module 1210; the vehicle operatordata receiving module 1213; the vehicle operator data transmissionmodule 1215; the vehicle identification number (VIN) data receivingmodule 1217; the VIN data transmission module 1220; the electronic datalogging device—vehicle data configuration module 1223; the electronicdata logging device—vehicle data configuration transmission module 1225;the vehicle data receiving module 1227; the time of day data receivingmodule 1230; the vehicle data, VIN data, vehicle operator data, and timeof day data correlation module 1232; the correlated data receivingmodule 1235; the correlated data reconciliation module 1238; the hoursof service (HOS) data generation module 1240; the gauges data generationmodule 1242; the driver vehicle inspection report (DVIR) data generationmodule 1245; the international fuel tax agreement (IFTA) data generationmodule 1247; the report data generation module 1250; the report datatransmission module 1252; or the report data receiving module 1255 maybe stored on the non-transitory computer-readable medium 1207 in theform of computer-readable instructions, any one of, all of, or anysub-combination of the user interface generation module 1210; thevehicle operator data receiving module 1213; the vehicle operator datatransmission module 1215; the vehicle identification number (VIN) datareceiving module 1217; the VIN data transmission module 1220; theelectronic data logging device—vehicle data configuration module 1223;the electronic data logging device—vehicle data configurationtransmission module 1225; the vehicle data receiving module 1227; thetime of day data receiving module 1230; the vehicle data, VIN data,vehicle operator data, and time of day data correlation module 1232; thecorrelated data receiving module 1235; the correlated datareconciliation module 1238; the hours of service (HOS) data generationmodule 1240; the gauges data generation module 1242; the driver vehicleinspection report (DVIR) data generation module 1245; the internationalfuel tax agreement (IFTA) data generation module 1247; the report datageneration module 1250; the report data transmission module 1252; or thereport data receiving module 1255 may be implemented by hardware (e.g.,one or more discrete component circuits, one or more applicationspecific integrated circuits (ASICs), etc.), firmware (e.g., one or moreprogrammable application specific integrated circuits (ASICs), one ormore programmable logic devices (PLDs), one or more field programmablelogic devices (FPLD), one or more field programmable gate arrays(FPGAs), etc.), and/or any combination of hardware, software and/orfirmware. Furthermore, the personal electronic device 1205 of FIG. 12may include one or more elements, processes and/or devices in additionto, or instead of, those illustrated in FIG. 12, and/or may include morethan one of, any, or all of the illustrated elements, processes anddevices.

Turning to FIG. 13, a method of operating a personal electronic device1300 may be implemented by a processor (e.g., a processor of thepersonal electronic device 120 of FIG. 1—“PED processor”) executing, forexample, modules 1210-1255 of FIG. 12. In particular, the PED processormay execute a user interface generation module 1210 to cause the PEDprocessor to generate a user interface (block 1305). The user interfacemay, for example, enable a user to enter personal data and vehicleidentification number (VIN) data. The personal data may includeinformation associated with a commercial motor vehicle (CMV) company andan individual that works for the CMV company. Thus, the personal datamay uniquely identify a particular vehicle operator. As describedelsewhere herein, the VIN data may be automatically acquired from anassociated vehicle control module in lieu of being entered by a user viathe user interface. The user interface may also enable a user to editvehicle data, personal data and/or any report data (e.g., HOS reportdata, DVIR report data, IFTA report data, vehicle original equipmentmanufacturer (OEM) report data, vehicle insurance company report data,etc.). For example, the user may, via the user interface, edit any ofthe data to correct errors, remove personal information, add data,remove data, reformat data, etc.

The PED processor may execute a vehicle operator data receiving module1213 to cause the PED processor to receive the personal data entered bythe user via the user interface (block 1307). The PED processor mayexecute a vehicle operator data transmission module 1215 to cause thePED processor to transmit the personal data to an associated vehicleelectronic device (e.g., vehicle electronic device 110 of FIG. 1) (block1310). The PED processor may execute a vehicle identification number(VIN) data receiving module 1217 to cause the PED processor to receivethe VIN data entered by the user via the user interface (block 1313).The PED processor may execute a VIN data transmission module 1220 tocause the PED processor to transmit the VIN data to an associatedvehicle electronic device (e.g., vehicle electronic device 110 ofFIG. 1) (block 1315).

The PED processor may execute an electronic data logging device—vehicledata configuration module 1223 to cause the PED processor to enable auser to configure an associated vehicle electronic device (e.g., vehicleelectronic device 110 of FIG. 1) (block 1318). For example, a user mayconfigure the vehicle electronic device 110 to acquire a desired set ofvehicle data from, for example, an associated vehicle electronic controlmodule (e.g., ECM 115 of FIG. 1) (block 1318). The user may also specifya time-interval which the vehicle electronic device 110 is to acquireany given vehicle data (block 1318). The user may configure the vehicleelectronic device 110 to acquire certain vehicle data more frequentlythan other vehicle data (block 1318). Alternatively, or additionally,any given vehicle electronic device 110 may be pre-configured to acquirepre-set vehicle data on a pre-set interval (block 1318).

The PED processor may execute an electronic data logging device—vehicledata configuration transmission module 1225 to cause the PED processorto transmit the vehicle electronic device configuration data to anassociated vehicle electronic device (e.g., vehicle electronic device110 of FIG. 1) (block 1320). The PED processor may execute a vehicledata receiving module 1227 to cause the PED processor to receive vehicledata from an associated vehicle electronic device (e.g., vehicleelectronic device 110 of FIG. 1) (block 1322).

The PED processor may execute a time of day data receiving module 1230to cause the PED processor to receive time of day data from, forexample, an associated vehicle electronic device (e.g., vehicleelectronic device 110 of FIG. 1) (block 1325). The time of day data maybe, for example, representative of a time associated with when vehicledata was acquired and a day on which the vehicle data was acquired.

The PED processor may execute a vehicle data, VIN data, vehicle operatordata, and time of day data correlation module 1232 to cause the PEDprocessor to correlate the vehicle data with the VIN data, the vehicleoperator data, and/or the time of day data (block 1328). For example,the PED processor may correlate the acquired vehicle data with acorresponding time and/or day at which the vehicle data was acquired orgenerated (block 1328). The PED processor may also correlate the vehicledata with a particular vehicle based on the VIN data (block 1328). ThePED processor may also correlate the vehicle data with a particularvehicle operator (block 1328).

The PED processor may execute a correlated data receiving module 1235 tocause the PED processor to receive, for example, correlated vehicle datafrom an associated vehicle electronic device (e.g., vehicle electronicdevice 110 of FIG. 1) (block 1330). As described elsewhere herein, thevehicle electronic device 110 may generate correlated vehicle data inlieu of the personal electronic device 120 generating the correlatedvehicle data.

The PED processor may execute a correlated data reconciliation module1238 to cause the PED processor to reconcile, for example, firstcorrelated vehicle data received from an associated vehicle electronicdevice (e.g., vehicle electronic device 110 of FIG. 1) with secondcorrelated vehicle data received from an associated remote electronicdevice (e.g., remote electronic device 525 of FIG. 5) (block 1332). As aresult of reconciling the first correlated vehicle data with the secondcorrelated vehicle data (block 1332), both the personal electronicdevice 120 and the remote electronic device 525 may store, for example,a complete and accurate set of correlated vehicle data. Accordingly, ifeither the personal electronic device 120 or the remote electronicdevice are unable to access correlated vehicle data for some period oftime (e.g., if either the personal electronic device 120 or the remoteelectronic device 525 is unable to communicate for some period of time)the vehicle data may be stored within a memory (e.g., memory 513 of FIG.5) of the vehicle electronic device 110.

Similarly, vehicle data corresponding to a particular user will not belost when, for example, the user does not log out of his personalelectronic device 120 and/or when the user leaves an associated vehicle(e.g., vehicle 105 of FIG. 1) to go to another vehicle (e.g., vehicle410 of FIG. 4) without having all of the vehicle data from the firstvehicle 105 stored and/or transmitted. The apparatuses, systems andmethods of the present disclosure may store vehicle data related to aparticular user in an associated vehicle electronic device 110 untilanother user logs onto (or registers with) the given vehicle electronicdevice 110, When another user logs onto (or registers with) a givenvehicle electronic device 110, the given vehicle electronic device maytransmit all stored vehicle data to a remote electronic device prior totransmitting a new user id, associated with the new user, to the remoteelectronic device via another personal device. Subsequently, the remoteelectronic device (which may store all complete vehicle data for eachuser, no matter where the data originated from) may provide any lostdata back to the personal electronic device of the first user.

The PED processor may execute an hours of service (HOS) data generationmodule 1240 to cause the PED processor to generate HOS data based on,for example, vehicle data, time of day data, and personal data (block1335). The PED processor may further generate an HOS display (e.g., HOSdisplay 210 of FIG. 2) based on the HOS data (block 1335).

The PED processor may execute a gauges data generation module 1242 tocause the PED processor to generate gauges data based on, for example,vehicle data (block 1338). The PED processor may generate gauges datathat is further based on time of day data (block 1338). The PEDprocessor may also generate a gauges display (e.g., gauges display 310of FIG. 3) based on the gauges data.

The PED processor may execute a driver vehicle inspection report (DVIR)data generation module 1245 to cause the PED processor to generate DVIRdata based on, for example, vehicle data (block 1340). The PED processormay generate DVIR data that is further based on time of day data and/orpersonal data (block 1340).

The PED processor may execute an international fuel tax agreement (IFTA)data generation module 1247 to cause the PED processor to generate IFTAdata based on, for example, vehicle data (block 1342). The PED processormay generate IFTA data that is further based on time of day data and/orpersonal data (block 1342).

The PED processor may execute a report data generation module 1250 tocause the PED processor to generate report data based on, for example,any one of the HOS data, the DVIR data, the IFTA data, the vehicle data,or the correlated vehicle data (block 1345). The PED processor mayexecute a report data transmission module 1252 to cause the PEDprocessor to transmit the report data to, for example, an associatedremote electronic device (e.g., remote electronic device 525 of FIG. 5)or a third party electronic device (e.g., a vehicle manufacture) (block1348). The PED processor may execute a report data receiving module 1255to cause the PED processor to receive report data from, for example, anassociated remote electronic device (e.g., remote electronic device 525of FIG. 5) (block 1350). As described elsewhere herein, a remoteelectronic device (REP) processor of the remote electronic device 525may generate report data based on, for example, HOS data, DVIR data,IFTA data, vehicle data, and/or correlated vehicle data.

As described above, the method 1300 may comprise a program (or module)for execution by a PED processor. The program (or module) may beembodied in software stored on a tangible (or non-transitory) computerreadable storage medium such as a compact disc read-only memory(“CD-ROM”), a floppy disk, a hard drive, a DVD, BLU-RAY® disk, or amemory associated with the PED processor. The entire program (or module)and/or parts thereof could alternatively be executed by a device otherthan the PED processor and/or embodied in firmware or dedicated hardware(e.g., one or more discrete component circuits, one or more applicationspecific integrated circuits (ASICs), etc.). Further, although theexample program (or module) is described with reference to the flowchartillustrated in FIG. 13, many other methods of implementing the method1300 may alternatively be used. For example, the order of execution ofthe blocks may be changed, and/or some of the blocks described may bechanged, eliminated, or combined.

With reference to FIG. 14, an electronic data logging system 1400 mayinclude a vehicle electronic device 1405 having a vehicle operator datareceiving module 1410; an electronic data logging device registrationdetermination module 1413; an electronic data logging device—vehicledata configuration receiving module 1415; a vehicle identificationnumber (VIN) data receiving module 1418; a VIN data transmission module1420; a vehicle data acquisition module 1423; a time of data receivingmodule 1425; a vehicle data, VIN data, vehicle operator data, and timeof day data correlation module 1428; a remote computing deviceconnectivity determination module 1430; a correlated data storage module1432; a correlated data transmission module 1435; and a storedcorrelated data transmission module 1438, stored on, for example, anon-transitory computer-readable medium 1406 in a form ofcomputer-readable instructions.

While any one of the vehicle operator data receiving module 1410; theelectronic data logging device registration determination module 1413;the electronic data logging device—vehicle data configuration receivingmodule 1415; the vehicle identification number (VIN) data receivingmodule 1418; the VIN data transmission module 1420; the vehicle dataacquisition module 1423; the time of data receiving module 1425; thevehicle data, VIN data, vehicle operator data, and time of day datacorrelation module 1428; the remote computing device connectivitydetermination module 1430; the correlated data storage module 1432; thecorrelated data transmission module 1435; or the stored correlated datatransmission module 1438 may be stored on the non-transitorycomputer-readable medium 1406 in a form of computer-readableinstructions, any one of, all of, or any sub-combination of the vehicleoperator data receiving module 1410; the electronic data logging deviceregistration determination module 1413; the electronic data loggingdevice—vehicle data configuration receiving module 1415; the vehicleidentification number (VIN) data receiving module 1418; the VIN datatransmission module 1420; the vehicle data acquisition module 1423; thetime of data receiving module 1425; the vehicle data, VIN data, vehicleoperator data, and time of day data correlation module 1428; the remotecomputing device connectivity determination module 1430; the correlateddata storage module 1432; the correlated data transmission module 1435;or the stored correlated data transmission module 1438 may beimplemented by hardware (e.g., one or more discrete component circuits,one or more application specific integrated circuits (ASICs), etc.),firmware (e.g., one or more programmable application specific integratedcircuits (ASICs), one or more programmable logic devices (PLDs), one ormore field programmable logic devices (FPLD), one or more fieldprogrammable gate arrays (FPGAs), etc.), and/or any combination ofhardware, software and/or firmware. Furthermore, the vehicle electronicdevice 1405 of FIG. 14 may include one or more elements, processesand/or devices in addition to, or instead of, those illustrated in FIG.14, and/or may include more than one of, any, or all of the illustratedelements, processes and devices.

Turning to FIG. 15, a method of operating a vehicle electronic device1500 may be implemented by a processor (e.g., a processor of the vehicleelectronic device 110 of FIG. 1—“VED processor”) executing, for example,modules 1410, 1413, 1415, 1423, 1430, 1432, 1438 of FIG. 14. Inparticular, a vehicle electronic device (e.g., vehicle electronic device110 of FIG. 1) is connected to a vehicle (e.g., vehicle 105 of FIG. 1)bus (e.g., vehicle bus 511, 512 of FIG. 5) (block 1505).

The VED processor may execute an electronic data logging deviceregistration determination module 1413 to cause the VED processor todetermine if the vehicle electronic device 110 is registered (block1510). The VED processor may determine that the vehicle electronicdevice 110 is registered if the VED processor has previously receivedpersonal data from, for example, an associated personal electronicdevice (e.g., personal electronic device 120 of FIG. 1). Alternatively,the VED processor may determine that the vehicle electronic device 110is registered if the VED processor has previously received personal dataand VIN data from, for example, an associated personal electronic device(e.g., personal electronic device 120 of FIG. 1) and VIN data from thepersonal electronic device 120 or an associated vehicle electroniccontrol module (e.g., ECM 115 of FIG. 1). Notably, vehicleidentification number (VIN) data may be automatically acquired from theECM 115 in lieu of being received from the personal electronic device120 when, for example, the VIN data is available via the ECM 115.

If the VED processor determines that the vehicle electronic device 110is not registered (block 1510), the VED processor may execute a vehicleoperator data receiving module 1410 to cause the VED processor toreceive personal data from, for example, an associated personalelectronic device (e.g., personal electronic device 120 of FIG. 1)(block 1515).

If the VED processor determines that the vehicle electronic device 110is registered (block 1510), the VED processor may execute a vehicle dataacquisition module 1423 to cause the VED processor to receive vehicledata from, for example, an associated vehicle electronic control module(e.g., ECM 115 of FIG. 1) (block 1520). The vehicle data may include,for example, any one of, all of, or any sub-combination of enginecontrol unit history data, air supply pressure data, fuel consumptiondata, trip information data, vehicle speed data, vehicle cruise controlstatus data, engine cooling fan drive status data, wheel speed data,vehicle service indication data, transmission control unit history data,body control unit history data, driver door status indicator data,passenger door indicator data, engine oil level data, engine oilpressure data, engine idle operation data, turbocharger status data, airstart pressure data, steering wheel angle data, vehicle accelerometerdata, vehicle pitch data, vehicle yaw data, vehicle distance data, idleshutdown data, engine hours data, engine revolutions data, time of daydata, date of year data, vehicle hours data, vehicle direction data,vehicle speed data, fuel consumption data, vehicle weight data, cruisecontrol speed set data, engine temperature data, power takeoffinformation data, fuel economy data, vehicle position(longitude/latitude/elevation) data, tire condition data, ambientconditions data, inlet air condition data, exhaust condition data,vehicle electrical power condition data, transmission fluid level data,transmission fluid pressure data, brake information data, engine coolantlevel data, engine coolant pressure data, vehicle odometer reading data,vehicle identification number data, crankcase pressure data, barometricpressure data, vehicle interior temperature data, air inlet temperaturedata, road surface temperature data, particulate trap inlet pressuredata, boost pressure data, intake manifold temperature data, air inletpressure data, air filter differential pressure data, exhaust gastemperature data, coolant filter differential pressure data,instantaneous fuel economy data, average fuel economy data, fueltemperature data, turbo oil temperature data, total fuel used data, tripfuel data, injector metering rail pressure data, injection controlpressure data, percent fan speed data, engine-percent torque demanddata, actual engine-percent torque data, accelerator pedal positiondata, percent load at current speed data, brake pedal position data,clutch pedal position data, water in fuel sensor data, etc.

The VED processor may execute a remote computing device connectivitydetermination module 1430 to determine if a remote computing device(e.g., a personal electronic device 120 of FIG. 1, or a remoteelectronic device 525 of FIG. 5) is communicatively connected to thevehicle electronic device 110 (block 1525). The VED processor maydetermine if a remote computing device is communicatively connected tothe vehicle electronic device 110 by, for example, pinging for remotecomputing devices proximate the vehicle electronic device (block 1525)

If the VED processor determines that a remote computing device is notcommunicatively connected to the vehicle electronic device 110 (block1525), the VED processor may execute a correlated data storage module1432 to cause the VED processor to store correlated vehicle data in amemory (e.g., storage memory 513 of FIG. 5) (block 1530).

If the VED processor determines that a remote computing device iscommunicatively connected to the vehicle electronic device 110 (block1525), the VED processor may execute a stored correlated datatransmission module 1438 to cause the VED processor to transmitcorrelated vehicle data and/or stored correlated vehicle data to, forexample, a remote computing device (e.g., a personal electronic device120 of FIG. 1, or a remote electronic device 525 of FIG. 5) (block1535).

As described above, the method 1500 may comprise a program (or module)for execution by a VED processor. The program (or module) may beembodied in software stored on a tangible (or non-transitory) computerreadable storage medium such as a compact disc read-only memory(“CD-ROM”), a floppy disk, a hard drive, a DVD, BLU-RAY® disk, or amemory associated with the VED processor. The entire program (or module)and/or parts thereof could alternatively be executed by a device otherthan the VED processor and/or embodied in firmware or dedicated hardware(e.g., one or more discrete component circuits, one or more applicationspecific integrated circuits (ASICs), etc.). Further, although theexample program (or module) is described with reference to the flowchartillustrated in FIG. 15, many other methods of implementing the method1500 may alternatively be used. For example, the order of execution ofthe blocks may be changed, and/or some of the blocks described may bechanged, eliminated, or combined.

With reference to FIG. 16, a method of operating a vehicle electronicdevice 1600 may be implemented by a processor (e.g., a processor of thevehicle electronic device 110 of FIG. 1—“VED processor”) executing, forexample, modules 1410-1438 of FIG. 14. In particular, the VED processormay execute a vehicle operator data receiving module 1410 to cause theVED processor to receive personal data from, for example, an associatedpersonal electronic device (e.g., personal electronic device 120 ofFIG. 1) (block 1605).

The VED processor may execute an electronic data logging deviceregistration determination module 1413 to cause the VED processor todetermine if the vehicle electronic device 110 is registered (block1607). The VED processor may determine that the vehicle electronicdevice 110 is registered if the VED processor has previously receivedpersonal data from, for example, an associated personal electronicdevice (e.g., personal electronic device 120 of FIG. 1). Alternatively,the VED processor may determine that the vehicle electronic device 110is registered if the VED processor has previously received personal dataand VIN data from, for example, an associated personal electronic device(e.g., personal electronic device 120 of FIG. 1) and VIN data from thepersonal electronic device 120 or an associated vehicle electroniccontrol module (e.g., ECM 115 of FIG. 1).

If the VED processor determines that the vehicle electronic device 110is not registered (block 1607), the VED processor may execute a vehicleoperator data receiving module 1410 to cause the VED processor toreceive personal data from, for example, an associated personalelectronic device (e.g., personal electronic device 120 of FIG. 1)(block 1605).

The VED processor may execute an electronic data logging device—vehicledata configuration receiving module 1415 to cause the VED processor toreceive vehicle electronic device configuration data (block 1610). Forexample, a user may configure the vehicle electronic device 110 toacquire a desired set of vehicle data from, for example, an associatedvehicle electronic control module (e.g., ECM 115 of FIG. 1) (block1610). The user may also specify a time-interval which the vehicleelectronic device 110 is to acquire any given vehicle data (block 1610).The user may configure the vehicle electronic device 110 to acquirecertain vehicle data more frequently than other vehicle data (block1610). Alternatively, or additionally, any given vehicle electronicdevice 110 may be pre-configured to acquire pre-set vehicle data on apre-set interval (block 1610).

The VED processor may execute a vehicle identification number (VIN) datareceiving module 1418 to cause the VED processor to receive VIN datafrom, for example, a vehicle control module (e.g., ECM 115 of FIG. 1) ora personal electronic device (e.g., a personal electronic device 120 ofFIG. 1) (block 1613). The VED processor may execute a VIN datatransmission module 1420 to cause the VED processor to transmit VIN datato, for example, a personal electronic device (e.g., a personalelectronic device 120 of FIG. 1) or a remote electronic device (e.g., aremote electronic device 525 of FIG. 5) (block 1615).

If the VED processor determines that the vehicle electronic device 110is registered (block 1607), the VED processor may execute a vehicle dataacquisition module 1423 to cause the VED processor to receive vehicledata from, for example, an associated vehicle electronic control module(e.g., ECM 115 of FIG. 1) (block 1618). The vehicle data may include,for example, any one of, all of, or any sub-combination of enginecontrol unit history data, air supply pressure data, fuel consumptiondata, trip information data, vehicle speed data, vehicle cruise controlstatus data, engine cooling fan drive status data, wheel speed data,vehicle service indication data, transmission control unit history data,body control unit history data, driver door status indicator data,passenger door indicator data, engine oil level data, engine oilpressure data, engine idle operation data, turbocharger status data, airstart pressure data, steering wheel angle data, vehicle accelerometerdata, vehicle pitch data, vehicle yaw data, vehicle distance data, idleshutdown data, engine hours data, engine revolutions data, time of daydata, date of year data, vehicle hours data, vehicle direction data,vehicle speed data, fuel consumption data, vehicle weight data, cruisecontrol speed set data, engine temperature data, power takeoffinformation data, fuel economy data, vehicle position(longitude/latitude/elevation) data, tire condition data, ambientconditions data, inlet air condition data, exhaust condition data,vehicle electrical power condition data, transmission fluid level data,transmission fluid pressure data, brake information data, engine coolantlevel data, engine coolant pressure data, vehicle odometer reading data,vehicle identification number data, crankcase pressure data, barometricpressure data, vehicle interior temperature data, air inlet temperaturedata, road surface temperature data, particulate trap inlet pressuredata, boost pressure data, intake manifold temperature data, air inletpressure data, air filter differential pressure data, exhaust gastemperature data, coolant filter differential pressure data,instantaneous fuel economy data, average fuel economy data, fueltemperature data, turbo oil temperature data, total fuel used data, tripfuel data, injector metering rail pressure data, injection controlpressure data, percent fan speed data, engine-percent torque demanddata, actual engine-percent torque data, accelerator pedal positiondata, percent load at current speed data, brake pedal position data,clutch pedal position data, water in fuel sensor data, etc.

The VED processor may execute a time of data receiving module 1425 tocause the VED processor to receive time of day data from, for example, avehicle control module (e.g., ECM 115 of FIG. 1) (block 1620). The timeof day data may be, for example, representative of a time associatedwith when vehicle data was acquired and a day on which the vehicle datawas acquired.

The VED processor may execute a vehicle data, VIN data, vehicle operatordata, and time of day data correlation module 1428 to cause the PEDprocessor to correlate the vehicle data with the VIN data, the vehicleoperator data, and/or the time of day data (block 1625). For example,the VED processor may correlate the acquired vehicle data with acorresponding time and/or day at which the vehicle data was acquired orgenerated (block 1625). The VED processor may also correlate the vehicledata with a particular vehicle based on the VIN data (block 1625). TheVED processor may also correlate the vehicle data with a particularvehicle operator (block 1625).

The VED processor may execute a remote computing device connectivitydetermination module 1430 to determine if a remote computing device(e.g., a personal electronic device 120 of FIG. 1, or a remoteelectronic device 525 of FIG. 5) is communicatively connected to thevehicle electronic device 110 (block 1628). The VED processor maydetermine if a remote computing device is communicatively connected tothe vehicle electronic device 110 by, for example, pinging for remotecomputing devices proximate the vehicle electronic device (block 1628)

If the VED processor determines that a remote computing device is notcommunicatively connected to the vehicle electronic device 110 (block1628), the VED processor may execute a correlated data storage module1432 to cause the VED processor to store correlated vehicle data in amemory (e.g., storage memory 513 of FIG. 5) (block 1630).

If the VED processor determines that a remote computing device is notcommunicatively connected to the vehicle electronic device 110 (block1628), the VED processor may execute a correlated data transmissionmodule 1435 to cause the VED processor to transmit correlated vehicledata and/or stored correlated vehicle data to a remote computing device(e.g., a personal electronic device 120 of FIG. 1, or a remoteelectronic device 525 of FIG. 5) (block 1633).

If the VED processor determines that a remote computing device iscommunicatively connected to the vehicle electronic device 110 (block1628), the VED processor may execute a stored correlated datatransmission module 1438 to cause the VED processor to transmitcorrelated vehicle data to, for example, a remote computing device(e.g., a personal electronic device 120 of FIG. 1, or a remoteelectronic device 525 of FIG. 5) (block 1635).

As described above, the method 1600 may comprise a program (or module)for execution by a VED processor. The program (or module) may beembodied in software stored on a tangible (or non-transitory) computerreadable storage medium such as a compact disc read-only memory(“CD-ROM”), a floppy disk, a hard drive, a DVD, BLU-RAY® disk, or amemory associated with the VED processor. The entire program (or module)and/or parts thereof could alternatively be executed by a device otherthan the VED processor and/or embodied in firmware or dedicated hardware(e.g., one or more discrete component circuits, one or more applicationspecific integrated circuits (ASICs), etc.). Further, although theexample program (or module) is described with reference to the flowchartillustrated in FIG. 16, many other methods of implementing the method1600 may alternatively be used. For example, the order of execution ofthe blocks may be changed, and/or some of the blocks described may bechanged, eliminated, or combined.

Turning to FIG. 17, an electronic data logging system 1700 may include aremote electronic device 1705 having a vehicle data receiving module1710; a time of day data receiving module 1713; a vehicle identificationnumber (VIN) data receiving module 1715; a vehicle data, VIN data,vehicle operator data, and time of day data correlation module 1718; acorrelated data receiving module 1720; a correlated data reconciliationmodule 1722; an hours of service (HOS) data generation module 1725; agauges data generation module 1728; a driver vehicle inspection report(DVIR) data generation module 1730; an international fuel tax agreement(IFTA) data module 1732; a report data generation module 1735; a reportdata transmission module 1738; and a report data receiving module 1740,stored on, for example, a non-transitory computer-readable medium 1706in the form of computer-readable instructions.

While any one of the vehicle data receiving module 1710; the time of daydata receiving module 1713; the vehicle identification number (VIN) datareceiving module 1715; the vehicle data, VIN data, vehicle operatordata, and time of day data correlation module 1718; the correlated datareceiving module 1720; the correlated data reconciliation module 1722;the hours of service (HOS) data generation module 1725; the gauges datageneration module 1728; the driver vehicle inspection report (DVIR) datageneration module 1730; the international fuel tax agreement (IFTA) datamodule 1732; the report data generation module 1735; the report datatransmission module 1738; or the report data receiving module 1740 maybe stored on the non-transitory computer-readable medium 1706 in theform of computer-readable instructions, any one of, all of, or anysub-combination of the vehicle data receiving module 1710; the time ofday data receiving module 1713; the vehicle identification number (VIN)data receiving module 1715; the vehicle data, VIN data, vehicle operatordata, and time of day data correlation module 1718; the correlated datareceiving module 1720; the correlated data reconciliation module 1722;the hours of service (HOS) data generation module 1725; the gauges datageneration module 1728; the driver vehicle inspection report (DVIR) datageneration module 1730; the international fuel tax agreement (IFTA) datamodule 1732; the report data generation module 1735; the report datatransmission module 1738; or the report data receiving module 1740 maybe implemented by hardware (e.g., one or more discrete componentcircuits, one or more application specific integrated circuits (ASICs),etc.), firmware (e.g., one or more programmable application specificintegrated circuits (ASICs), one or more programmable logic devices(PLDs), one or more field programmable logic devices (FPLD), one or morefield programmable gate arrays (FPGAs), etc.), and/or any combination ofhardware, software and/or firmware. Furthermore, the remote electronicdevice 1705 of FIG. 17 may include one or more elements, processesand/or devices in addition to, or instead of, those illustrated in FIG.17, and/or may include more than one of, any, or all of the illustratedelements, processes and devices.

With reference to FIG. 18, a method of operating a vehicle electronicdevice 1800 may be implemented by a processor (e.g., a processor of theremote electronic device 525 of FIG. 5—“RED processor”) executing, forexample, modules 1710-1740 of FIG. 17. In particular, the RED processormay execute a vehicle data acquisition module 1710 to cause the REDprocessor to receive vehicle data from, for example, an associatedvehicle electronic control module (e.g., ECM 115 of FIG. 1) (block1805). The vehicle data may include, for example, any one of, all of, orany sub-combination of engine control unit history data, air supplypressure data, fuel consumption data, trip information data, vehiclespeed data, vehicle cruise control status data, engine cooling fan drivestatus data, wheel speed data, vehicle service indication data,transmission control unit history data, body control unit history data,driver door status indicator data, passenger door indicator data, engineoil level data, engine oil pressure data, engine idle operation data,turbocharger status data, air start pressure data, steering wheel angledata, vehicle accelerometer data, vehicle pitch data, vehicle yaw data,vehicle distance data, idle shutdown data, engine hours data, enginerevolutions data, time of day data, date of year data, vehicle hoursdata, vehicle direction data, vehicle speed data, fuel consumption data,vehicle weight data, cruise control speed set data, engine temperaturedata, power takeoff information data, fuel economy data, vehicleposition (longitude/latitude/elevation) data, tire condition data,ambient conditions data, inlet air condition data, exhaust conditiondata, vehicle electrical power condition data, transmission fluid leveldata, transmission fluid pressure data, brake information data, enginecoolant level data, engine coolant pressure data, vehicle odometerreading data, vehicle identification number data, crankcase pressuredata, barometric pressure data, vehicle interior temperature data, airinlet temperature data, road surface temperature data, particulate trapinlet pressure data, boost pressure data, intake manifold temperaturedata, air inlet pressure data, air filter differential pressure data,exhaust gas temperature data, coolant filter differential pressure data,instantaneous fuel economy data, average fuel economy data, fueltemperature data, turbo oil temperature data, total fuel used data, tripfuel data, injector metering rail pressure data, injection controlpressure data, percent fan speed data, engine-percent torque demanddata, actual engine-percent torque data, accelerator pedal positiondata, percent load at current speed data, brake pedal position data,clutch pedal position data, water in fuel sensor data, etc.

The RED processor may execute a time of data receiving module 1713 tocause the RED processor to receive time of day data from, for example, avehicle control module (e.g., ECM 115 of FIG. 1) (block 1810). The timeof day data may be, for example, representative of a time associatedwith when vehicle data was acquired and a day on which the vehicle datawas acquired.

The RED processor may execute a vehicle identification number (VIN) datareceiving module 1715 to cause the VED processor to receive VIN datafrom, for example, a vehicle control module (e.g., ECM 115 of FIG. 1) ora personal electronic device (e.g., a personal electronic device 120 ofFIG. 1) (block 1813).

The RED processor may execute a vehicle data, VIN data, vehicle operatordata, and time of day data correlation module 1718 to cause the PEDprocessor to correlate the vehicle data with the VIN data, the vehicleoperator data, and/or the time of day data (block 1815). For example,the RED processor may correlate the acquired vehicle data with acorresponding time and/or day at which the vehicle data was acquired orgenerated (block 1815). The RED processor may also correlate the vehicledata with a particular vehicle based on the VIN data (block 1815). TheRED processor may also correlate the vehicle data with a particularvehicle operator (block 1815).

The RED processor may execute a correlated data receiving module 1720 tocause the RED processor to receive, for example, correlated vehicle datafrom an associated vehicle electronic device (e.g., vehicle electronicdevice 110 of FIG. 1) (block 1820). As described elsewhere herein, thevehicle electronic device 110 may generate correlated vehicle data inlieu of the remote electronic device 525 generating the correlatedvehicle data.

The RED processor may execute a correlated data reconciliation module1722 to cause the RED processor to reconcile, for example, firstcorrelated vehicle data received from an associated vehicle electronicdevice (e.g., vehicle electronic device 110 of FIG. 1) with secondcorrelated vehicle data received from an associated remote electronicdevice (e.g., remote electronic device 525 of FIG. 5) (block 1825). As aresult of reconciling the first correlated vehicle data with the secondcorrelated vehicle data (block 1825), both the personal electronicdevice 120 and the remote electronic device 525 may store, for example,a complete and accurate set of correlated vehicle data. Accordingly, ifeither the personal electronic device 120 or the remote electronicdevice are unable to access correlated vehicle data for some period oftime (e.g., if either the personal electronic device 120 or the remoteelectronic device 525 is unable to communicate for some period of time).

The RED processor may execute an hours of service (HOS) data generationmodule 1725 to cause the RED processor to generate HOS data based on,for example, vehicle data, time of day data, and personal data (block1830). The RED processor may further generate an HOS display (e.g., HOSdisplay 210 of FIG. 2) based on the HOS data (block 1830).

The RED processor may execute a gauges data generation module 1728 tocause the RED processor to generate gauges data based on, for example,vehicle data (block 1835). The RED processor may generate gauges datathat is further based on time of day data (block 1835). The REDprocessor may also generate a gauges display (e.g., gauges display 310of FIG. 3) based on the gauges data.

The RED processor may execute a driver vehicle inspection report (DVIR)data generation module 1730 to cause the RED processor to generate DVIRdata based on, for example, vehicle data (block 1840). The RED processormay generate DVIR data that is further based on time of day data and/orpersonal data (block 1840).

The RED processor may execute an international fuel tax agreement (IFTA)data generation module 1732 to cause the RED processor to generate IFTAdata based on, for example, vehicle data (block 1845). The RED processormay generate IFTA data that is further based on time of day data and/orpersonal data (block 1845).

The RED processor may execute a report data generation module 1735 tocause the RED processor to generate report data based on, for example,any one of the HOS data, the DVIR data, the IFTA data, the vehicle data,or the correlated vehicle data (block 1850). The RED processor mayexecute a report data transmission module 1738 to cause the REDprocessor to transmit the report data to, for example, an associatedremote electronic device (e.g., remote electronic device 525 of FIG. 5)or a third party electronic device (e.g., a vehicle manufacture) (block1855). The RED processor may execute a report data receiving module 1740to cause the RED processor to receive report data from, for example, anassociated remote electronic device (e.g., remote electronic device 525of FIG. 5) (block 1860). The REP processor may generate report databased on, for example, HOS data, DVIR data, IFTA data, vehicle data,and/or correlated vehicle data.

Additionally, the RED processor may execute a user interface generationmodule 1210 to cause the RED processor to generate a user interface. Theuser interface may, for example, enable a user to enter personal dataand vehicle identification number (VIN) data. The personal data mayinclude information associated with a commercial motor vehicle (CMV)company and an individual that works for the CMV company. Thus, thepersonal data may uniquely identify a particular vehicle operator. Asdescribed elsewhere herein, the VIN data may be automatically acquiredfrom an associated vehicle control module in lieu of being entered by auser via the user interface. The user interface may also enable a userto edit vehicle data, personal data and/or any report data (e.g., HOSreport data, DVIR report data, IFTA report data, vehicle originalequipment manufacturer (OEM) report data, vehicle insurance companyreport data, etc.). For example, the user may, via the user interface,edit any of the data to correct errors, remove personal information, adddata, remove data, reformat data, etc.

As described above, the method 1800 may comprise a program (or module)for execution by a RED processor. The program (or module) may beembodied in software stored on a tangible computer readable storagemedium such as a compact disc read-only memory (“CD-ROM”), a floppydisk, a hard drive, a DVD, BLU-RAY® disk, or a memory associated withthe RED processor. The entire program (or module) and/or parts thereofcould alternatively be executed by a device other than the RED processorand/or embodied in firmware or dedicated hardware (e.g., one or morediscrete component circuits, one or more application specific integratedcircuits (ASICs), etc.). Further, although the example program (ormodule) is described with reference to the flowchart illustrated in FIG.18, many other methods of implementing the method 1800 may alternativelybe used. For example, the order of execution of the blocks may bechanged, and/or some of the blocks described may be changed, eliminated,or combined.

Numerous modifications to the apparatuses, systems, and methodsdisclosed herein will be apparent to those skilled in the art in view ofthe foregoing description. Accordingly, this description is to beconstrued as illustrative only, and is presented for the purpose ofenabling those skilled in the art to make and use the invention and toteach the preferred mode of carrying out same. The exclusive rights toall modifications within the scope of the disclosure and the appendedclaims are reserved.

What is claimed is:
 1. A vehicle electronic device, comprising: aprocessor and a memory within the vehicle electronic device; a vehicledata acquisition module, stored on the memory within the vehicleelectronic device, that, when executed by the processor within thevehicle electronic device, causes the processor to receive vehicle datafrom a vehicle via a data bus of the vehicle, wherein the vehicle dataincludes vehicle odometer information; a time data acquisition module,stored on the memory within the vehicle electronic device, that, whenexecuted by the processor within the vehicle electronic device, causesthe processor to receive time data, wherein the time data includesinformation related to a time of day; a time-stamped vehicle datageneration module, stored on the memory within the vehicle electronicdevice, that, when executed by the processor within the vehicleelectronic device, causes the processor to generate time-stamped vehicledata based on the vehicle data and the time data, wherein thetime-stamped vehicle data includes the vehicle data correlated with thetime data; a personal data acquisition module, stored on the memorywithin the vehicle electronic device, that, when executed by theprocessor within the vehicle electronic device, causes the processor toreceive personal data, wherein the personal data includes informationassociated with at least one vehicle operator; a correlated vehicle datageneration module, stored on the memory within the vehicle electronicdevice, that, when executed by the processor within the vehicleelectronic device, causes the processor within the vehicle electronicdevice to generate correlated vehicle data based on the time-stampedvehicle data and the personal data, wherein the correlated vehicle datais representative of an association between the time-stamped vehicledata and the personal data; and a personal electronic deviceavailability determination module, stored on the memory within thevehicle electronic device, that, when executed by the processor withinthe vehicle electronic device, causes the processor to determine whetherthe vehicle electronic device is communicatively coupled with a personalelectronic device, wherein when the processor determines that thevehicle electronic device is communicatively coupled with the personalelectronic device, the processor transmits the correlated vehicle datato the personal electronic device, and wherein when the processordetermines that the vehicle electronic device is not communicativelycoupled with the personal electronic device, the processor stores thecorrelated vehicle data on the memory of the vehicle electronic device.2. The device of claim 1, wherein the vehicle data is received from avehicle electronic control module via at least one of: a J1939 protocolvehicle data bus, a J1708 protocol vehicle data bus, or an OBDIIprotocol vehicle data bus.
 3. The device of claim 1, further comprising:a data transmission module, stored on the memory, that, when executed bythe processor, causes the processor to transmit the correlated vehicledata to a remote electronic device.
 4. The device of claim 1, whereinthe vehicle data is filtered into a set of parameters for generatinghours of service data, wherein the filtered parameters include at leastone of: vehicle position data, vehicle engine revolution per minutedata, vehicle speed data, vehicle odometer data, or vehicle engineoperating hour data.
 5. The device of claim 1, further comprising: avehicle electronic device registration module, stored on the memory,that, when executed by the processor, causes the processor to registerthe vehicle electronic device with a particular vehicle operator basedon the personal data and the vehicle data, wherein the vehicle dataincludes vehicle identification number data, and wherein the personaldata includes particular vehicle operator data.
 6. A non-transitory,computer-readable, medium, comprising: a personal data acquisitionmodule that, when executed by a processor within a vehicle electronicdevice, causes the processor to receive personal data, wherein thepersonal data includes information associated with a particular vehicleoperator; a vehicle electronic device registration determination modulethat, when executed by the processor of the vehicle electronic device,causes the processor to register the vehicle electronic device with theparticular user in response to receiving the personal data; a vehicledata acquisition module that, when executed by the processor, causes theprocessor to receive vehicle data, directly from a vehicle via a databus of the vehicle, at the vehicle electronic device when the processordetermines that the vehicle electronic device is registered with theparticular vehicle operator, wherein the vehicle data includes vehicleodometer information; a time data acquisition module that, when executedby the processor, causes the processor to receive time data at theprocessor of the vehicle electronic device, wherein the time dataincludes information related to a time of day; a time-stamped vehicledata generation module that, when executed by the processor, causes theprocessor to generate time-stamped vehicle data, wherein thetime-stamped vehicle data includes the vehicle data correlated with thetime data; and a personal electronic device availability determinationmodule that, when executed by the processor, causes the processor todetermine whether the vehicle electronic device is communicativelycoupled with a personal electronic device, wherein when the processordetermines that the vehicle electronic device is communicatively coupledwith the personal electronic device, the processor transmits thecorrelated vehicle data to the personal electronic device, and whereinwhen the processor determines that the vehicle electronic device is notcommunicatively coupled with the personal electronic device, theprocessor stores the correlated vehicle data on a memory of the vehicleelectronic device.
 7. The non-transitory, computer-readable, medium ofclaim 6, further comprising: a data transmission module that, whenexecuted by a processor, causes the processor to transmit the correlatedvehicle data to a remote electronic device.
 8. The non-transitory,computer-readable, medium of claim 7, wherein the memory is either aflash memory or an electrically erasable programmable read-only memory.9. The non-transitory, computer-readable, medium of claim 6, wherein thevehicle data is received from a vehicle via at least one of: a J1939protocol vehicle data bus, a J1708 protocol vehicle data bus, or anOBDII protocol vehicle data bus.
 10. The non-transitory,computer-readable, medium of claim 6, wherein the vehicle data includesat least one of: engine control unit history data, air supply pressuredata, fuel consumption data, trip information data, vehicle speed data,vehicle cruise control status data, engine cooling fan drive statusdata, wheel speed data, vehicle service indication data, transmissioncontrol unit history data, body control unit history data, driver doorstatus indicator data, passenger door indicator data, engine oil leveldata, engine oil pressure data, engine idle operation data, turbochargerstatus data, air start pressure data, steering wheel angle data, vehicleaccelerometer data, vehicle pitch data, vehicle yaw data, vehicledistance data, idle shutdown data, engine hours data, engine revolutionsdata, time of day data, date of year data, vehicle hours data, vehicledirection data, fuel consumption data, vehicle weight data, cruisecontrol speed set data, engine temperature data, power takeoffinformation data, fuel economy data, vehicle position(longitude/latitude/elevation) data, tire condition data, ambientconditions data, inlet air condition data, exhaust condition data,vehicle electrical power condition data, transmission fluid level data,transmission fluid pressure data, brake information data, engine coolantlevel data, engine coolant pressure data, vehicle odometer reading data,vehicle identification number data, crankcase pressure data, barometricpressure data, vehicle interior temperature data, air inlet temperaturedata, road surface temperature data, particulate trap inlet pressuredata, boost pressure data, intake manifold temperature data, air inletpressure data, air filter differential pressure data, exhaust gastemperature data, coolant filter differential pressure data,instantaneous fuel economy data, average fuel economy data, fueltemperature data, turbo oil temperature data, total fuel used data, tripfuel data, injector metering rail pressure data, injection controlpressure data, percent fan speed data, engine-percent torque demanddata, actual engine-percent torque data, accelerator pedal positiondata, percent load at current speed data, brake pedal position data,clutch pedal position data, or water in fuel sensor data.
 11. Anelectronic data logging system, comprising: a personal electronic devicehaving a first processor and a first memory; a personal data acquisitionmodule, stored on the first memory, that, when executed by the firstprocessor, causes the first processor to receive personal data, whereinthe personal data includes information associated with at least onevehicle operator; and a personal data transmission module, stored on thefirst memory, that, when executed by the first processor, causes thefirst processor to transmit the personal data to a vehicle electronicdevice that is registered with a particular vehicle operator; and thevehicle electronic device having a second processor and a second memory;a personal data receiving module, stored on the second memory, that,when executed by the second processor, causes the second processor toreceive the personal data from the first processor; a vehicle dataacquisition module, stored on the second memory, that, when executed bythe second processor, causes the second processor to receive vehicledata, directly from a vehicle via a data bus of the vehicle, in responseto receiving the personal data, wherein the vehicle data includes atleast one of: vehicle position data, vehicle engine revolution perminute data, vehicle speed data, vehicle odometer data, or vehicleengine operating hour data; a time data acquisition module, stored onthe second memory, that, when executed by the second processor, causesthe second processor to receive time data, wherein the time dataincludes information related to a time of day; a time-stamped vehicledata generation module, stored on the second memory, that, when executedby the second processor, causes the second processor to generatetime-stamped vehicle data, wherein the time-stamped vehicle dataincludes the vehicle data correlated with the time data; and a personalelectronic device availability determination module, stored on thesecond memory, that, when executed by the second processor, causes thesecond processor to determine whether the vehicle electronic device iscommunicatively coupled with the personal electronic device, whereinwhen the second processor determines that the vehicle electronic deviceis communicatively coupled with the personal electronic device, thesecond processor transmits the time-stamped vehicle data to the personalelectronic device, and wherein when the second processor determines thatthe vehicle electronic device is not communicatively coupled with thepersonal electronic device, the second processor stores the time-stampedvehicle data on the second memory.
 12. The system of claim 11, furthercomprising: an hours of service data generation module, stored on thefirst memory, that, when executed by the first processor, causes thefirst processor to generate hours of service data, wherein the hours ofservice data is representative of at least one of: a number of hours thevehicle operator was off duty, a number of hours the vehicle operatorwas in a sleeper birth, a number of hours the vehicle operator wasdriving, or a number of hours the operator was on duty but not driving.13. The system of claim 11, further comprising: an hours of service datastorage module, stored on the first memory, that, when executed by thefirst processor, causes the first processor to store hours of servicedata on the first memory.
 14. The system of claim 11, wherein thevehicle data is received from a vehicle electronic control unit via atleast one of: a J1939 protocol vehicle data bus, a J1708 protocolvehicle data bus, or an OBDII protocol vehicle data bus.
 15. The systemof claim 11, wherein the vehicle data is filtered into a desired set ofparameters.
 16. The system of claim 11, wherein the first memory iseither a flash memory or an electrically erasable programmable read-onlymemory.
 17. The system of claim 11, wherein the second memory is eithera flash memory or an electrically erasable programmable read-onlymemory.
 18. The system of claim 11, further comprising: a datatransmission module, stored on the first memory, that, when executed bythe first processor, causes the first processor to transmit thetime-stamped vehicle data to a remote electronic device.
 19. The systemof claim 11, further comprising: a data transmission module, stored onthe second memory, that, when executed by the second processor, causesthe second processor to transmit the time-stamped vehicle data to aremote electronic device.
 20. The system of claim 11, furthercomprising: a correlated vehicle data generation module, stored on thesecond memory, that, when executed by the second processor, causes thesecond processor to generate correlated vehicle data, wherein thecorrelated vehicle data is representative of an association between thetime-stamped vehicle data and the personal data.
 21. The system of claim11, further comprising: a remote electronic device, comprising; a thirdprocessor and a third memory; a correlated vehicle data receivingmodule, stored on the third memory, that, when executed by the thirdprocessor, causes the third processor to receive correlated vehicle datafor the personal electronic device.
 22. The system of claim 11, furthercomprising: a remote electronic device, comprising; a third processorand a third memory; a correlated vehicle data receiving module, storedon the third memory, that, when executed by the third processor, causesthe third processor to receive correlated vehicle data for the vehicleelectronic device.